Show index and memory mode in debugger tooltip #39
Conversation
I'm currently trying to get started with reverse engineering SNES games, and as far as I could tell this information as not otherwise exposed, even though Mesen records it.:wq
|
Thanks for the PR/idea - it could be useful to show this in some way, yea. I'll have to take a look at how this could be added - I think there are a couple more scenarios where specific CPUs have some special flags in the CDL data that might be relevant, too. There's no bug tracker atm, unfortunately I already have such a huge backlog of things I have to fix/improve or that people have requested already that I prefer to keep the issues tab off for the time being to keep the workload manageable. That said, there's a thread on the NesDev forums for Mesen where people often report bugs, etc., so that's probably the best way to publicly report bugs/make requests at the moment. |
|
I fully understand the desire to not have a huge backlog of issues here on GitHub 😅 What do you think of enabling the GitHub discussions feature here in the repo, that way it would at least be possible to talk about potential features in a threaded way that's tied to the repo? 🤔 |
|
Regarding the tooltip info, let me know where this would be best implemented. I would be up for implementing it, also for other CPUs if needed. |
I'm currently trying to get started with reverse engineering SNES games, and as far as I could tell this information as not otherwise exposed, even though Mesen records it.
I don't really expect this to get merged in its current form, given that it's relatively SNES specific. But I didn't see a good way to start a discussion about whether this would make sense (there's no bugtracker right?), so let me know what you think 🙂
PS: Thanks for all your work 🚀